I am a firm supporter of the OLC; L wrote an article for my club
newsletter and gave a presentation at our monthly meeting using a
modification of Reiner's 2005 SSA OLC one.

However, I'm having a dickens of a time uploading my flight traces to
the OLC.
Use a Cambridge GPS Model 20 and L-NAV.
Extract *.cai file from GPS.
Use the protocol suggested by OLC to convert and tag the traces.
Can't get *.igc file accepted by OLC using either SeeYou or OLC Flight
Claim methods.
The OLC helper has been able to get my traces on OLC. But, he and I
would rather spend the time doing more fun things!
And, I'm not alone out here in Ephrata. I watch my soaring buddies
with Cam 20 GPS go through the same frustration. None of us are
computer geeks, but we are far from newbies (my first home "PC" was a
Timex 1000). My buddies are engineers with lots of computer "hands on"
experience.
Anyone having better success and would share their step by step method?
Could send to me by e-mail unless others are having the same problem.

Open *.CAI file with SeeYou. Optimize (Edit->Optiize or Ctrl+L) flight.
Click submit button. Make sure "automaticly upload flight" is checked in
submit dialog. Click submit button.

Thats it.

Just make sure you open the *.cai file directly with SeYou. It will do
the rest.




Roy Clark, B6 wrote:
> I am a firm supporter of the OLC; L wrote an article for my club
> newsletter and gave a presentation at our monthly meeting using a
> modification of Reiner's 2005 SSA OLC one.
>
> However, I'm having a dickens of a time uploading my flight traces to
> the OLC.
> Use a Cambridge GPS Model 20 and L-NAV.
> Extract *.cai file from GPS.
> Use the protocol suggested by OLC to convert and tag the traces.
> Can't get *.igc file accepted by OLC using either SeeYou or OLC Flight
> Claim methods.
> The OLC helper has been able to get my traces on OLC. But, he and I
> would rather spend the time doing more fun things!
> And, I'm not alone out here in Ephrata. I watch my soaring buddies
> with Cam 20 GPS go through the same frustration. None of us are
> computer geeks, but we are far from newbies (my first home "PC" was a
> Timex 1000). My buddies are engineers with lots of computer "hands on"
> experience.
> Anyone having better success and would share their step by step method?
> Could send to me by e-mail unless others are having the same problem.
>

"Roy Clark, B6" > wrote in message
oups.com...
>I am a firm supporter of the OLC; L wrote an article for my club
> newsletter and gave a presentation at our monthly meeting using a
> modification of Reiner's 2005 SSA OLC one.
>
> However, I'm having a dickens of a time uploading my flight traces to
> the OLC.
> Use a Cambridge GPS Model 20 and L-NAV.
> Extract *.cai file from GPS.

How are you "extracting" the file from the logger? It may be corrupted that
way. If you are using the first version of Connect Me it requires it to be
downloaded twice. They have corrected that but if you haven't gotten the
update then it could still be a problem.

I download flights from my Model 25 (same thing just external antenna) with
an Ipaq running Connect Me, place it in on a SD card, upload it via a card
reader into my PC, use See You 3.1 to analyze it and optimize it then send
it to OLC with no problems on the uploading end.

OLC however is very sensitive to what most would consider minor errors e.g.
wrong birthdate, engine running if you didn't check "pure glider", missing
data if you turned the logger on then off briefly before takeoff, misspelled
name to name a few. They nicely list all the errors in red at the bottom of
the attempted upload so that you have a chance to correct them. What errors
are you seeing there?

Casey Lenox
KC
Phoenix

Thanks.



David Leonard wrote:
> Open *.CAI file with SeeYou. Optimize (Edit->Optiize or Ctrl+L)
flight.
> Click submit button. Make sure "automaticly upload flight" is checked
in
> submit dialog. Click submit button.
>
> Thats it.
>
> Just make sure you open the *.cai file directly with SeYou. It will
do
> the rest.

Don't use Connect Me or Ipaq.

Have been using the method described in FAQ on the OLC.

I'm having the same problem uploading a pair of log files from a
friend's old Model 20. I've tried uploading "by hand" via the OLC
flight claim page, and massaging all of the data fields by hand. I've
tried uploading with SeeYou 3.1, but when the OLC flight claim page
comes up, it has different coordinates for the turnpoints than SeeYou
selected. When I change those coordinates to match what SeeYou came up
with, it comes back with a message saying "No valid fixes after end of
flight" or something similar. I am a computer programmer by trade, and
I manage a couple of web sites, so I like to think there isn't operator
error involved here.

The only thing I can find that might be causing the trouble is that in
each log file, there are about a half dozen "B" records with east
longitudes instead of west. I think that might be confusing the server
software. But when I edit the file and remove or modify those records,
OLC complains about something else ...

-ted/2NO

When I go through all the proper (manual) procedures for the 7 May
flight at the OLC web page and click on "Check entry", the first time
OLC crunches all the data it comes back with *no*error*messages* and
all 7 flight points (start/1/2/3/4/5/finish) in green.

It also has the 1st and 3d waypoints in the eastern hemisphere and a
total flight distance of 42263.26 km. Now that's a heck of a flight!!!

Even though this page has no error messages, it still does not have a
"Claim Flight" button.

When I then modify the points to exactly match what SeeYou reports, the
distance becomes correct, but the 4th, 5th, and finish points are no
longer labeled in green, and the following error messages are reported:

"The finish time is after the end of the flight without propulsion.
This is not allowed. Please adjust the finish time or the time of the
end of the flight without propulsion.
Valid waypoints reached in the present flight trace (IGC-file) are
printed in green.
The flight claim is complete only when all waypoints are printed in
green.
Suggestions will be made by the server only if the flight trace
approaches a declared waypoint to no more than 2.5km.
There is no fix in the IGC-file with your finish time. "

.... which makes no sense at all.

As a software engineer I admire what the OLC team has done, but as a
user, I sure hope they fix this, or tell me how I can get around it!

-ted/2NO

A correction to my most recent post. I had wrong "End of flight without
propulsion" time entered. With the correct launch/soar/finish/land
times, these are the error messages I get:

"Valid waypoints reached in the present flight trace (IGC-file) are
printed in green.
The flight claim is complete only when all waypoints are printed in
green.
Suggestions will be made by the server only if the flight trace
approaches a declared waypoint to no more than 2.5km.
There is no fix in the IGC-file with your finish time."

It's that last one that's frustrating me. I have verified multiple
times that there is in fact a fix in the IGC file with exactly the
finish time...

-ted/2NO

2NO wrote:
> I get:
> "Valid waypoints reached in the present flight trace (IGC-file) are
> printed in green.
> The flight claim is complete only when all waypoints are printed in
> green.
> Suggestions will be made by the server only if the flight trace
> approaches a declared waypoint to no more than 2.5km.
> There is no fix in the IGC-file with your finish time."

I have exactly the same problem (Cambridge Model 10). I have reviewed
the raw file and confirmed that there are indeed B record fixes in the
file corresponding to the fixes that OLC is showing as no good.

> I have verified multiple
> times that there is in fact a fix in the IGC file with exactly the
> finish time...

Ditto.

I have tried - CAI file direct to See-You 2.85. I have tried CAI file
+ conv-cam to create new IGC file then the OLC utility cai2igc to
append the G records to the new IGC file & several variations thereon.
All equally hopeless and resulting in the same errors as you have. I
have wasted hours on this and I'm giving up unless someone has the
process down.

wrote:
> 2NO wrote:
> > I get:
> > "Valid waypoints reached in the present flight trace (IGC-file) are
> > printed in green.
> > The flight claim is complete only when all waypoints are printed in
> > green.
> > Suggestions will be made by the server only if the flight trace
> > approaches a declared waypoint to no more than 2.5km.
> > There is no fix in the IGC-file with your finish time."
>
> I have exactly the same problem (Cambridge Model 10). I have
reviewed
> the raw file and confirmed that there are indeed B record fixes in
the
> file corresponding to the fixes that OLC is showing as no good.
>
> > I have verified multiple
> > times that there is in fact a fix in the IGC file with exactly the
> > finish time...
>
> Ditto.
>
> I have tried - CAI file direct to See-You 2.85. I have tried CAI
file
> + conv-cam to create new IGC file then the OLC utility cai2igc to
> append the G records to the new IGC file & several variations
thereon.
> All equally hopeless and resulting in the same errors as you have. I
> have wasted hours on this and I'm giving up unless someone has the
> process down.

I had a very similar problem last year. With the help of the OLC team,
it was determined that the file transfer to OLC was incomplete, so many
B records were missing on the file on their system. I tried to upload
the file again and was rebuffed with the message "Flight File already
in OLC" or some such ... it wouldn't replace the partial file with a
new copy.

Again, the OLC team provided a trick that allowed me to eventually be
successful. The trick is to change the name of the .igc file to be
uploaded by bumping up the flight sequence number for the flight date.
That's the digit in the eighth character position in the file name.

Example: change ymdCxxx1.igc to ymdCxxx2.igc

OLC treats the new file as if it is a new file for a new claim, giving
a new shot at getting the complete file uploaded.

wrote:
> 2NO wrote:
> > I get:
> > "Valid waypoints reached in the present flight trace (IGC-file) are
> > printed in green.
> > The flight claim is complete only when all waypoints are printed in
> > green.
> > Suggestions will be made by the server only if the flight trace
> > approaches a declared waypoint to no more than 2.5km.
> > There is no fix in the IGC-file with your finish time."
>
> I have exactly the same problem (Cambridge Model 10). I have
reviewed
> the raw file and confirmed that there are indeed B record fixes in
the
> file corresponding to the fixes that OLC is showing as no good.
>
> > I have verified multiple
> > times that there is in fact a fix in the IGC file with exactly the
> > finish time...
>
> Ditto.
>
> I have tried - CAI file direct to See-You 2.85. I have tried CAI
file
> + conv-cam to create new IGC file then the OLC utility cai2igc to
> append the G records to the new IGC file & several variations
thereon.
> All equally hopeless and resulting in the same errors as you have. I
> have wasted hours on this and I'm giving up unless someone has the
> process down.

I had a very similar problem last year. With the help of the OLC team,
it was determined that the file transfer to OLC was incomplete, so many
B records were missing on the file on their system. I tried to upload
the file again and was rebuffed with the message "Flight File already
in OLC" or some such ... it wouldn't replace the partial file with a
new copy.

Again, the OLC team provided a trick that allowed me to eventually be
successful. The trick is to change the name of the .igc file to be
uploaded by bumping up the flight sequence number for the flight date.
That's the digit in the eighth character position in the file name.

Example: change ymdCxxx1.igc to ymdCxxx2.igc

OLC treats the new file as if it is a new file for a new claim, giving
a new shot at getting the complete file uploaded.

Tuno,
I was just looking at a flight one of your ASA buddies (YB - yellow
belly?) made on Saturday. Noticed it was truncated on the OLC display
while they were still several thousand feet in the air. Downloaded the
*.igc file, and the rest of the flight was there in the B records, all
the way to landing. SeeYou could show the whole flight and came up with
a much longer distance.

I don't have a way to check the appended *.cai file, but it could be
truncated on the server. I have had an incomplete upload of a file in
the past, without any understandable error message, or obvious way to
recover. That would explain the security failure reported. Could also be
because the B records in the igc file were edited. Don't know what the
OLC server does when it finds B records that don't match whats in the
appended *.CAI file. It could stop processing the log right there.
Tweaking the B records in the file is a no-no and will cause a security
failure with these secure log files.

Either might explain your error messages. You could try re-uploading as
mentioned earlier in this thread with a modified file name.

-Dave Leonard
ZL


Bob S wrote:
> wrote:
>
>>2NO wrote:
>>
>>> I get:
>>>"Valid waypoints reached in the present flight trace (IGC-file) are
>>>printed in green.
>>>The flight claim is complete only when all waypoints are printed in
>>>green.
>>>Suggestions will be made by the server only if the flight trace
>>>approaches a declared waypoint to no more than 2.5km.
>>>There is no fix in the IGC-file with your finish time."
>>
>>I have exactly the same problem (Cambridge Model 10). I have
>
> reviewed
>
>>the raw file and confirmed that there are indeed B record fixes in
>
> the
>
>>file corresponding to the fixes that OLC is showing as no good.
>>
>>
>>>I have verified multiple
>>>times that there is in fact a fix in the IGC file with exactly the
>>>finish time...
>>
>>Ditto.
>>
>>I have tried - CAI file direct to See-You 2.85. I have tried CAI
>
> file
>
>>+ conv-cam to create new IGC file then the OLC utility cai2igc to
>>append the G records to the new IGC file & several variations
>
> thereon.
>
>>All equally hopeless and resulting in the same errors as you have. I
>>have wasted hours on this and I'm giving up unless someone has the
>>process down.
>
>
> I had a very similar problem last year. With the help of the OLC team,
> it was determined that the file transfer to OLC was incomplete, so many
> B records were missing on the file on their system. I tried to upload
> the file again and was rebuffed with the message "Flight File already
> in OLC" or some such ... it wouldn't replace the partial file with a
> new copy.
>
> Again, the OLC team provided a trick that allowed me to eventually be
> successful. The trick is to change the name of the .igc file to be
> uploaded by bumping up the flight sequence number for the flight date.
> That's the digit in the eighth character position in the file name.
>
> Example: change ymdCxxx1.igc to ymdCxxx2.igc
>
> OLC treats the new file as if it is a new file for a new claim, giving
> a new shot at getting the complete file uploaded.
>

Bob,

That was one of the first things I tried, but got the same results.

Still stuck, and have just a few hours left ...

ted/2NO

There's a nice how-to .pdf document on the 1-26 Association web site here:

http://www.126association.org/docs/OLC.pdf

Has lots of good tips for a trouble-free upload. Credits to Tom Pressley and
B. Resor and others.

Jim

"Roy Clark, B6" > wrote in message
oups.com...
>I am a firm supporter of the OLC; L wrote an article for my club
> newsletter and gave a presentation at our monthly meeting using a
> modification of Reiner's 2005 SSA OLC one.
>
> However, I'm having a dickens of a time uploading my flight traces to
> the OLC.
> Use a Cambridge GPS Model 20 and L-NAV.
> Extract *.cai file from GPS.
> Use the protocol suggested by OLC to convert and tag the traces.
> Can't get *.igc file accepted by OLC using either SeeYou or OLC Flight
> Claim methods.
> The OLC helper has been able to get my traces on OLC. But, he and I
> would rather spend the time doing more fun things!
> And, I'm not alone out here in Ephrata. I watch my soaring buddies
> with Cam 20 GPS go through the same frustration. None of us are
> computer geeks, but we are far from newbies (my first home "PC" was a
> Timex 1000). My buddies are engineers with lots of computer "hands on"
> experience.
> Anyone having better success and would share their step by step method?
> Could send to me by e-mail unless others are having the same problem.
>

Thanks Dave. Where did you find YB's flight to download?! And which one
did you find? I've uploaded four versions and can't find them anywhere
(have never got to the page with the "Claim Flight" button).

Hack hack hack
-ted/2NO

I just tried again with a log file from YB's SN10, but I now get this
error message:

"The flight can not be scored, because it is outside the claim time
window.
The flight is in the BHC claim window. It may be possible to claim it
there."

I thought we had until midnight local time Tuesday for uploads?

*Sigh* time for a beer.

-eltedro/2NO

I have wondered about this "midnight local time" rule. How does a
server in Germany know our local time in the USA, where we have multiple
time zones? Is the deadline really midnight on the East Coast?
Midnight in Germany? Midnight in Greenwich? Just another OLC issue
that is not clear from their website.



2NO wrote:
> I just tried again with a log file from YB's SN10, but I now get this
> error message:
>
> "The flight can not be scored, because it is outside the claim time
> window.
> The flight is in the BHC claim window. It may be possible to claim it
> there."
>
> I thought we had until midnight local time Tuesday for uploads?
>
> *Sigh* time for a beer.
>
> -eltedro/2NO
>

It was right there on the May 7 Daily score page. 557c2242.igc Its gone now.

Deadline must be midnight EST for the whole US? Kind of annoying.

2NO wrote:
> Thanks Dave. Where did you find YB's flight to download?! And which one
> did you find? I've uploaded four versions and can't find them anywhere
> (have never got to the page with the "Claim Flight" button).
>
> Hack hack hack
> -ted/2NO
>

2NO wrote:

> I just tried again with a log file from YB's SN10, but I now get this
> error message:
>
> "The flight can not be scored, because it is outside the claim time
> window.
> The flight is in the BHC claim window. It may be possible to claim it
> there."
>
> I thought we had until midnight local time Tuesday for uploads?
>
> *Sigh* time for a beer.
>
> -eltedro/2NO
>
Tuno!

Thanks for all the effort! I tried submitting My YB flight vis See
You 3.1 and it worked the first time. The CAI Model 20 is going in for
service. Hope we don't all have to go thru this again.

It was a fun flight, but submitting it took more tiome than the 333 miles!

Wonderful to hear, Paul!

But are you going to let ZL call you Yellow Belly?!

Oh, the humanity!!!

2NO

"Paul M. Cordell" > wrote in message
...
> 2NO wrote:
>
>> I just tried again with a log file from YB's SN10, but I now get this
>> error message:
>>
>> "The flight can not be scored, because it is outside the claim time
>> window.
>> The flight is in the BHC claim window. It may be possible to claim it
>> there."
>>
>> I thought we had until midnight local time Tuesday for uploads?
>>
>> *Sigh* time for a beer.
>>
>> -eltedro/2NO
>>
> Tuno!
>
> Thanks for all the effort! I tried submitting My YB flight vis See You
> 3.1 and it worked the first time. The CAI Model 20 is going in for
> service. Hope we don't all have to go thru this again.
>
> It was a fun flight, but submitting it took more tiome than the 333 miles!

2NO wrote:
> When I then modify the points to exactly match what SeeYou reports, the
> distance becomes correct, but the 4th, 5th, and finish points are no
> longer labeled in green, and the following error messages are reported:
>
> "The finish time is after the end of the flight without propulsion.
> This is not allowed. Please adjust the finish time or the time of the
> end of the flight without propulsion.
> Valid waypoints reached in the present flight trace (IGC-file) are
> printed in green.
> The flight claim is complete only when all waypoints are printed in
> green.
> Suggestions will be made by the server only if the flight trace
> approaches a declared waypoint to no more than 2.5km.
> There is no fix in the IGC-file with your finish time. "
>
> ... which makes no sense at all.

It might be that the times (take-off, departure, finish) are off by one
hour. If the altitude reported at the finish time is too high or the
position is not what it should be then try to advance the finish time.

Harri

2NO wrote:
> I just tried again with a log file from YB's SN10, but I now get this
> error message:
>
> "The flight can not be scored, because it is outside the claim time
> window.
> The flight is in the BHC claim window. It may be possible to claim it
> there."
>
> I thought we had until midnight local time Tuesday for uploads?
>
> *Sigh* time for a beer.
>
> -eltedro/2NO
My experience - email them and explain your problem - extremely helpful and
unbeurocratic. They will probably ask for the original file via mail and sort it
out for you. (At least that was my experience when I first got my LX20 and made
a mess of things...)

--
Bruce Greeff
Std Cirrus #57
I'm no-T at the address above.
-+-
\_________0_________/

Roy Clark, B6 wrote:
> Don't use Connect Me or Ipaq.
>
> Have been using the method described in FAQ on the OLC.
>

So have you had any success yet?

Just tried my first submission, and finally got it to work
(using a CAI model 20). Two minor hitches, had a yellow V
indication which took a full day to turn green, and still
have an ENL error showing, even though I declared pure glider.

Method was to use SeeYou to download the trace, and prepare the
..olc file. Then used the cai2igc utility to create a new igc
file, and went to the web site and manually uploaded the new
files. The "submit to" boxes in SeeYou were empty, so couldn't
try that. Next time I'll try the more automated ways available.

People haven't been mentioning what software versions they've
been using, which could be important. I used SeeYou 2.82, with
the OLC-USA patch installed. Firmware in the model 20 was upgraded
to 6.0.

-Dave

David Leonard wrote:
> Tuno,
> I was just looking at a flight one of your ASA buddies (YB - yellow
> belly?) made on Saturday. Noticed it was truncated on the OLC display
> while they were still several thousand feet in the air. Downloaded the
> *.igc file, and the rest of the flight was there in the B records, all
> the way to landing. SeeYou could show the whole flight and came up with
> a much longer distance.
>
> I don't have a way to check the appended *.cai file, but it could be
> truncated on the server. I have had an incomplete upload of a file in
> the past, without any understandable error message, or obvious way to
> recover.

Can't you just edit the flight, and hit Remove Flight to recover from this?

> People haven't been mentioning what software versions they've
> been using, which could be important. I used SeeYou 2.82, with
> the OLC-USA patch installed. >
> -Dave

Anyone else having a problem with the "OLC Patch"? I dowloaded from
the SeeYou site, but the SeeYou still tries to upload to the old URL as
far as I can tell (ie. ~/2004). If this would work (ie. directly
submitting from SeeYou), it looks like by far the lowest hassle factor.


P3

The most recent OLC patch I know of adds the US region support.

In any case, SeeYou 3.1 does the automatic upload for me just fine.

-Tom